pg_dump core dump, upgrading from 6.5b1 to 5/24 snapshot - Mailing list pgsql-hackers

From Ari Halberstadt
Subject pg_dump core dump, upgrading from 6.5b1 to 5/24 snapshot
Date
Msg-id v04003a05b370a37a10be@[207.244.108.39]
Whole thread Raw
Responses Re: [HACKERS] pg_dump core dump, upgrading from 6.5b1 to 5/24 snapshot  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hi,

I posted a related question yesterday to the general list, but Bruce
Momjian <maillist@candle.pha.pa.us> suggested it belongs on the hackers
list.

Using pg_dump with 6.5b1 on solaris sparc crashes with a core dump. This
means I can't keep backups and I can't upgrade my data model without being
able to export the old data.

On Bruce's suggestion I tried upgrading to a recent snapshot (in this case
the one from 5/24). When I killed the old postmaster and started the new
postmaster I got the following error in psql:

bboard=> \d
ERROR:  nodeRead: Bad type 0

which sounds to me like maybe there was a change in the data format. Since
I can't use pg_dump to get my data out of 6.5b1 I'm a bit stuck now. For
now I've (quickly) gone back to using 6.5b1 and not the snapshot.

If one of the developers wants debug info on the coredump let me know what
you need (e.g., what commands to do in gdb--though I'll have to install
this or get run permissions from the sysadmin). I did a quick stack trace
in adb and it was dead in a call to fprintf, which I know does nothing to
help pinpoint the bug but it sounds like a typical way to kill a C program.

-- Ari Halberstadt mailto:ari@shore.net <http://www.magiccookie.com/>
PGP public key available at <http://www.magiccookie.com/pgpkey.txt>




pgsql-hackers by date:

Previous
From: The Hermit Hacker
Date:
Subject: Re: [HACKERS] Call for updates!
Next
From: ZEUGSWETTER Andreas IZ5
Date:
Subject: Re: create index updates nrows statistics